Data Services Developer's Guide : How To Create Physical Data Services from Relational Tables and Views
This page last changed on Jan 09, 2008 by tkatz.
eDocs Home > BEA AquaLogic Data Services Platform 3.0 Documentation > Data Services Developer's Guide
|
Relational Type | Description |
---|---|
Tables and Views |
Displays all public tables and views in the selected data source. |
Stored Procedures |
Displays all public stored procedures in the selected data source. |
SQL Statement |
Allows creation of a SQL statement for extracting relational data from the data source. |
Database Function |
Allows creation of an XQuery function in a library data service based on build-in or custom database functions. |
To create a physical data service based on a relational table or view:
A list of available database table and view SQL objects appears.
Objects are grouped based on the relational data sources catalog and/or schema.
In the example of an RTLCUSTOMER catalog, the ADDRESS and CUSTOMER tables both become physical data services.
![]() | Database-specific Catalog and Schema Considerations |
Simply check the desired objects or their container, which will select all enclosed tables or views.
If you click on an individual object such as ADDRESS or CUSTOMER, information describing the database's primary key(s), column name, type and nullability appears. For example the CUSTOMER table contains a CUSTOMER_ID field of type VARCHAR. That column is not nullable, meaning that it must be supplied with any updates.
Each new entity data service is created with a Read function that contains all the metadata elements identified during data service creation. It can be thought of as comparable to the following construct in the relational world:
select * from <table>
Use the Properties dialog to:
![]() | In some cases this option may not be available. |
The root element, which is read-only, is also displayed.
![]() | Initially the root element name matches the name of the data service. |
There are several default naming conventions associated with new data services:
![]() | XML Name Conversion Considerations |
On the Review New Data Service(s) page you can set, confirm or, optionally, change suggested data service names depending on the type of physical data service you are creating.
The nominated name for a new data service is, wherever possible, the same as the source object name. In some cases, however, names are adjusted to conform with XML naming conventions.
![]() | XML Name Conversion Considerations |
Name conflicts occur when there is a data service of the same name present in the target directory. Name conflicts are highlighted in red.
There are several situations where you will need to change the name of your data service:
Data services always have the file extension:
.ds
Database vendors variously support database catalogs and schemas.
Vendor | Catalog | Schema |
---|---|---|
Oracle | Does not support catalogs. When specifying database objects, the catalog field should be left blank. | Typically the name of an Oracle user ID. |
DB2 | If specifying database objects, the catalog field should be left blank. | Schema name corresponds to the catalog owner of the database, such as db2admin. |
Sybase | Catalog name is the database name. | Schema name corresponds to the database owner. |
Microsoft SQL Server | Catalog name is the database name. | Schema name corresponds to the catalog owner, such as dbo. The schema name must match the catalog or database owner for the database to which you are connected. |
Informix | Does not support catalogs. If specifying database objects, the catalog field should be left blank. | Not needed. |
PointBase | PointBase database systems do not support catalogs. If specifying database objects, the catalog field should be left blank. | Schema name corresponds to a database name. |
When a source name is encountered that does not fit within XML naming conventions, default generated names are converted according to rules described by the SQLX standard. Generally speaking, an invalid XML name character is replaced by its hexadecimal escape sequence (having the form xUUUU).
For additional details see section 9.1 of the W3C draft version of this standard:
![]() |
Document generated by Confluence on Jan 15, 2008 11:02 |